Skip to content

Conversation

@elmiko
Copy link
Contributor

@elmiko elmiko commented May 5, 2021

This change updates all the machine api providers to use the proper go
versions depending on the openshift release. It is being made to address
issues with go vet that arising due to an old golang version (1.13).

For all the providers the following changes have been made:

  • master, 4.8, and 4.9 now use go lang 1.16 as the base image
  • 4.7 now uses go lang 1.15 as the base image

This change is needed by:
openshift/cluster-api-provider-kubevirt#35
openshift/cluster-api-provider-openstack#180
openshift/cluster-api-provider-baremetal#151
openshift/cluster-api-provider-ovirt#103

Given the size of this change, I would like to get sign off from the following teams

  • Machine API
  • oVirt
  • OpenStack
  • libvirt
  • baremetal
  • kubevirt

This change updates all the machine api providers to use the proper go
versions depending on the openshift release. It is being made to address
issues with `go vet` that arising due to an old golang version (1.13).

For all the providers the following changes have been made:
* master, 4.8, and 4.9 now use go lang 1.16 as the base image
* 4.7 now uses go lang 1.15 as the base image
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elmiko
To complete the pull request process, please assign emilienm, enxebre, rgolangh, stbenjam after the PR has been reviewed.
You can assign the PR to them by writing /assign @emilienm @enxebre @rgolangh @stbenjam in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@elmiko
Copy link
Contributor Author

elmiko commented May 5, 2021

/assign @EmilienM @enxebre @rgolangh @stbenjam

@Danil-Grigorev
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 5, 2021
@stbenjam
Copy link
Member

stbenjam commented May 5, 2021

/approve

Some on-going flakes with metal ipi, but the ones that passed looked good and nothing failed in an unexpected way.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 5, 2021

@elmiko: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/cluster-api-provider-ovirt/master/e2e-ovirt f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.8/e2e-metal-ipi-ovn-ipv6 f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.9/e2e-metal-ipi-ovn-ipv6 f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/master/e2e-metal-ipi-ovn-ipv6 f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.8/e2e-metal-ipi f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.8/e2e-metal-ipi-ovn-dualstack f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.9/e2e-metal-ipi-ovn-dualstack f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/master/e2e-metal-ipi-ovn-dualstack f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.8/e2e-metal-ipi-virtualmedia f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.8/e2e-metal-ipi-upgrade f6ff3a7 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.9/e2e-metal-ipi-upgrade f6ff3a7 link /test pj-rehearse
ci/prow/pj-rehearse f6ff3a7 link /test pj-rehearse

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rgolangh
Copy link
Contributor

rgolangh commented May 6, 2021

/assign @Gal-Zaidman

@mandre
Copy link
Member

mandre commented May 6, 2021

/lgtm

@cfergeau
Copy link
Contributor

cfergeau commented May 6, 2021

/lgtm

@nirarg
Copy link
Contributor

nirarg commented May 6, 2021

/lgtm

@Gal-Zaidman
Copy link
Contributor

/lgtm

@Gal-Zaidman
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 9, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfergeau, Danil-Grigorev, elmiko, Gal-Zaidman, mandre, nirarg, stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 9, 2021
@openshift-merge-robot openshift-merge-robot merged commit 275158f into openshift:master May 9, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 9, 2021

@elmiko: Updated the following 4 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-api-provider-aws-master.yaml using file ci-operator/config/openshift/cluster-api-provider-aws/openshift-cluster-api-provider-aws-master.yaml
    • key openshift-cluster-api-provider-azure-master.yaml using file ci-operator/config/openshift/cluster-api-provider-azure/openshift-cluster-api-provider-azure-master.yaml
    • key openshift-cluster-api-provider-baremetal-master.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-master.yaml
    • key openshift-cluster-api-provider-gcp-master.yaml using file ci-operator/config/openshift/cluster-api-provider-gcp/openshift-cluster-api-provider-gcp-master.yaml
    • key openshift-cluster-api-provider-kubevirt-master.yaml using file ci-operator/config/openshift/cluster-api-provider-kubevirt/openshift-cluster-api-provider-kubevirt-master.yaml
    • key openshift-cluster-api-provider-libvirt-master.yaml using file ci-operator/config/openshift/cluster-api-provider-libvirt/openshift-cluster-api-provider-libvirt-master.yaml
    • key openshift-cluster-api-provider-openstack-master.yaml using file ci-operator/config/openshift/cluster-api-provider-openstack/openshift-cluster-api-provider-openstack-master.yaml
    • key openshift-cluster-api-provider-ovirt-master.yaml using file ci-operator/config/openshift/cluster-api-provider-ovirt/openshift-cluster-api-provider-ovirt-master.yaml
  • ci-operator-4.8-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-api-provider-aws-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-aws/openshift-cluster-api-provider-aws-release-4.8.yaml
    • key openshift-cluster-api-provider-azure-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-azure/openshift-cluster-api-provider-azure-release-4.8.yaml
    • key openshift-cluster-api-provider-baremetal-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-release-4.8.yaml
    • key openshift-cluster-api-provider-gcp-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-gcp/openshift-cluster-api-provider-gcp-release-4.8.yaml
    • key openshift-cluster-api-provider-kubevirt-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-kubevirt/openshift-cluster-api-provider-kubevirt-release-4.8.yaml
    • key openshift-cluster-api-provider-libvirt-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-libvirt/openshift-cluster-api-provider-libvirt-release-4.8.yaml
    • key openshift-cluster-api-provider-openstack-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-openstack/openshift-cluster-api-provider-openstack-release-4.8.yaml
    • key openshift-cluster-api-provider-ovirt-release-4.8.yaml using file ci-operator/config/openshift/cluster-api-provider-ovirt/openshift-cluster-api-provider-ovirt-release-4.8.yaml
  • ci-operator-4.9-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-api-provider-aws-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-aws/openshift-cluster-api-provider-aws-release-4.9.yaml
    • key openshift-cluster-api-provider-azure-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-azure/openshift-cluster-api-provider-azure-release-4.9.yaml
    • key openshift-cluster-api-provider-baremetal-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-release-4.9.yaml
    • key openshift-cluster-api-provider-gcp-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-gcp/openshift-cluster-api-provider-gcp-release-4.9.yaml
    • key openshift-cluster-api-provider-kubevirt-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-kubevirt/openshift-cluster-api-provider-kubevirt-release-4.9.yaml
    • key openshift-cluster-api-provider-libvirt-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-libvirt/openshift-cluster-api-provider-libvirt-release-4.9.yaml
    • key openshift-cluster-api-provider-openstack-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-openstack/openshift-cluster-api-provider-openstack-release-4.9.yaml
    • key openshift-cluster-api-provider-ovirt-release-4.9.yaml using file ci-operator/config/openshift/cluster-api-provider-ovirt/openshift-cluster-api-provider-ovirt-release-4.9.yaml
  • ci-operator-4.7-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-api-provider-baremetal-release-4.7.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-release-4.7.yaml
    • key openshift-cluster-api-provider-libvirt-release-4.7.yaml using file ci-operator/config/openshift/cluster-api-provider-libvirt/openshift-cluster-api-provider-libvirt-release-4.7.yaml
    • key openshift-cluster-api-provider-openstack-release-4.7.yaml using file ci-operator/config/openshift/cluster-api-provider-openstack/openshift-cluster-api-provider-openstack-release-4.7.yaml
    • key openshift-cluster-api-provider-ovirt-release-4.7.yaml using file ci-operator/config/openshift/cluster-api-provider-ovirt/openshift-cluster-api-provider-ovirt-release-4.7.yaml
Details

In response to this:

This change updates all the machine api providers to use the proper go
versions depending on the openshift release. It is being made to address
issues with go vet that arising due to an old golang version (1.13).

For all the providers the following changes have been made:

  • master, 4.8, and 4.9 now use go lang 1.16 as the base image
  • 4.7 now uses go lang 1.15 as the base image

This change is needed by:
openshift/cluster-api-provider-kubevirt#35
openshift/cluster-api-provider-openstack#180
openshift/cluster-api-provider-baremetal#151
openshift/cluster-api-provider-ovirt#103

Given the size of this change, I would like to get sign off from the following teams

  • Machine API
  • oVirt
  • OpenStack
  • libvirt
  • baremetal
  • kubevirt

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@elmiko elmiko deleted the update-mapi-provider-golang branch May 10, 2021 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.